Feeding updates to landing pages of users of an online social network from external sources

ABSTRACT

Updates to landing pages of users in an online social network are fed from external sources so that content maintained by any one user can be consolidated in a single location regardless of where the changes are made to the content. When an update event occurs, users of the online social network are notified according to various criteria that they have set. With this feature, users can browse through content of other users efficiently.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No. 11/531,154, filed Sep. 12, 2006, entitled “Method and System for Tracking Changes to User Content in an Online Social Network.”

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to processing of online social network data, and more particularly, to a method and system for feeding updates to user landing pages from external sources.

2. Description of the Related Art

Over the past several years, the amount of personal information that individuals share online has increased dramatically. Many web sites provide an online community that provides content focusing on a common interest or theme, and allows people to join the online community and share personal information with other users of the online community. Online social networking sites have also been rapidly gaining in popularity. Typically, users of an online social network communicate with one another and meet other users based on personal information captured in the profiles or landing pages of other users.

Also, users of online social networks often request their existing friends to join, creating a web of online relationships that mirror offline ones. Operators of online social networking sites typically require that new users provide certain personal information to join, including contact information (e.g., physical and e-mail addresses, telephone numbers, instant messaging nicknames, etc.) and identifying information (e.g. a name, location, personal interests, age, etc.).

A positive consequence of this general trend is the greater ability for groups of friends, families and other acquaintances to communicate online with, and about, each other as users of a social network. For example, a group of friends may share personal information with each other about common interests, individual personal attributes, events, schedules and activity plans and may also access each others' personal information. Another benefit of online social networks is that their users can more easily find others who share common interests, goals, lifestyles, etc., without being limited to an online community dedicated to a particular interest. Doing so allows members to expand their social networks.

With access to cheap storage and higher bandwidths, the amount of information stored by users of online social networks has grown exponentially. In addition to profile information, the users now often store large amounts of multimedia files, including blogs, digital photos, and digital audio and video files. As a consequence, the process of browsing the content of other users has become highly inefficient.

In addition, as more and more interesting web sites and online communities are being created, individuals are joining multiple ones to benefit from the services provided by them. The downside of all this is that individuals maintain their content under multiple profiles and it is becoming increasingly difficult to share them efficiently with others.

The web site, onxiam, permits a user to consolidate all of his or her online identities in a single location and present them as hyperlinks on a web page that can be made accessible to anyone who wants to learn about the user's multiple online identities. In Yahoo! 360°, users maintain a personal web site through which they can maintain a blog, share their photos using a feed from Flickr, present profile information, subscribe to external feeds, and see which friends are currently online.

SUMMARY OF THE INVENTION

The present invention provides a method and system for feeding updates to landing pages of users in an online social network from external sources, so that the efficiency of finding and viewing content associated with users is much improved. According to embodiments of the present invention, updates that a user of an online social network makes at another web site are automatically reflected on the user's landing page maintained by the online social network. Even though the user maintains a blog at another web site, stores photos at still another web site, and uploads videos on yet another web site, updates that the user makes at any of these web sites will automatically be reflected on the user's landing page. In addition, when an update event occurs, other users of the online social network are notified according to various criteria that they have set.

A method according to a first embodiment of the present invention includes the steps of receiving updates to a landing page of a first user, notifying a second user of the updates, receiving a request for the landing page of the first user from the second user, generating a landing page of the first user, and transmitting the landing page to the second user for display. In the above recited method, the first user's landing page includes content that is retrieved from a local database and content that is supplied from an external database. The content may be a blog, a photo collection, or a video collection.

A method according to a second embodiment of the present invention includes the steps of receiving a web page that indicates updates to a landing page of a first user, issuing a request for the landing page of the first user in response to a second user's input, receiving the landing page of the first user, and displaying the landing page of the first user to the second user. In the above recited method, the first user's landing page is managed by a web site for an online social network and includes content that is retrieved from a database that is maintained by this web site and content that is supplied from a different web site. The content may be a blog, a photo collection, or a video collection.

A server computer according to an embodiment of the present invention includes a user database that maintains a landing page for a first user and tracking preferences of a second user, and a processing unit that is programmed to carry out the steps of (i) receiving and storing updates to the landing page of the first user including updates from a client computer of the first user and updates from an external computer, and (ii) if any of the updates is of a type included in the tracking preferences of the second user, notifying the second user of the updates.

The advantages of the method and system according to embodiments of the present invention are several. First, a person who wants to learn about the user and his or her interests is able to access such information at a central location, i.e., the user's landing page. The person need not serially access the different web sites that contain the user's content. Second, a friend of the user need not constantly browse through the content the user is maintaining at the different web sites to see if such content has been updated. Third, a person can define a filter for the content updates by selecting the users that he or she would like to track and the type of content updates that he or she is interested in tracking. Fourth, a person can select different ways of being notified of the content updates as well as the frequency of the notifications.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.

FIG. 1 is a diagram that graphically represents the relationships between users of an online social network;

FIG. 2 is a block diagram illustrating components of a system for managing an online social network;

FIG. 3 schematically illustrates the process for tracking changes and updates to content in an online social network and managing the notification of such changes and updates;

FIG. 4A is a schematic illustration of a web page used to specify various notification settings;

FIG. 4B is a schematic illustration of a web page used to communicate changes and updates to user content;

FIG. 5 is a flow diagram illustrating the process steps for filtering the changes and updates to user content;

FIG. 6 is a schematic illustration of a landing page for a particular user and external content sources for the landing page;

FIG. 7 is a flow diagram illustrating the process steps carried out by a server computer for an online social network when notifying users of updates to landing pages and generating the landing pages upon request; and

FIG. 8 is a flow diagram illustrating the process steps carried out by a client computer connected to a server computer for an online social network when notifying a user of updates to a landing page of another user and displaying the landing page to the user.

DETAILED DESCRIPTION

FIG. 1 is a graph representation of a social network centered on a given individual (ME). Other users of this social network include A-U whose position, relative to ME's, is referred to by the degree of separation between ME and each other user. Friends of ME, which includes A, B, and C, are separated from ME by one degree of separation (1 d/s). A friend of a friend of ME is separated from ME by 2 d/s. As shown, D, E, F, G, and H are each separated from ME by 2 d/s. A friend of a friend of a friend of ME is separated from ME by 3 d/s. FIG. 1 depicts all nodes separated from ME by more than 3 degrees of separation as belonging to the category ALL.

Degrees of separation in a social network are defined relative to an individual. For example, in ME's social network, H and ME are separated by 2 d/s, whereas in G's social network, H and G are separated by only 1 d/s. Accordingly, each individual will have their own set of first, second and third degree relationships.

As those skilled in the art understand, an individual's social network may be extended to include nodes to an Nth degree of separation. As the number of degrees increases beyond three, however, the number of nodes typically grows at an explosive rate and quickly begins to mirror the ALL set.

FIG. 2 is a block diagram illustrating a system 250 for creating and managing an online social network. The system 250 represents one example embodiment of a system for creating and managing an online social network, and includes an application server 251 and one or more graph servers 252. As known in the art, a server is a computer having a processing unit and system memory that is programmed to carry out certain functions. The system 250 is connected to a network 260, e.g., the Internet, and accessible over the network by a plurality of remote computers (only three of which are shown), collectively designated as 270.

The application server 251 manages a user database 254, a relationship database 255, a search database 256, and other databases 257. The user database 254 contains profile information for each of the user in the online social network managed by the system 250. The profile information may include, among other things: a unique user identifier (user ID), name, age, gender, location, hometown, references to image files, listing of interests, attributes, and the like. The user database 254 also contains information about groups (e.g., organizations, school alumni associations, family, etc.) that users have defined. The group information may include, among other things: a unique group identifier (group ID), name, description of the group, and members of the group. The relationship database 255 stores for each user, the user IDs of all users with whom the user has a direct relationship, i.e., direct friends of the user who are users of the online social network. In addition, the contents of the user database 254 are indexed and optimized for search, and stored in the search database 256. The other databases 257 may include a database for storing testimonials, and various other information commonly stored in online social networks and communities. The user database 254, the relationship database 255, the search database 256, and the other databases 257 are updated to reflect inputs of new user information and edits of existing user information that are made through the remote computers 270.

The application server 251 also manages the information exchange requests that it receives from the remote computers 270. The graph servers 252 receive a query from the application server 251, process the query and return the query results to the application server 251. The graph servers 252 manage a representation of the social network for all users in the member database. The graph servers 252 have a dedicated memory device 253, such as a random access memory (RAM), in which an adjacency list that indicates all first degree relationships in the social network is stored. The graph servers 252 respond to requests from application server 251 to identify relationships and the degree of separation between users of the online social network.

In the embodiments of the present invention described below, users are respectively operating the remote computers 270 that are programmed to execute web browser programs, and access the web pages managed by the application server 251 using the web browser programs. The web pages that are displayed to a user are transmitted from the application server 251 to that user's remote computer and processed by the web browser program stored in that user's remote computer for display through the monitor of that user's remote computer.

FIG. 3 schematically illustrates the process for tracking changes and updates to content in an online social network and managing the notification of such changes and. Blocks 310, 320, 330, 335, 340 represent the operations that are being carried out by the application server 251. Block 312 represents the user inputs that are made through a browser running on a remote computer and are transmitted over the Internet to the application server 251. Block 314 represents certain inputs that are made at third party web sites 314, such as flickr, YouTube, xanga.com, and eBay, and transmitted over the Internet to the application server 251 using an RSS feed. All such inputs are aggregated and stored in a queue 310 that is managed by the application server 251.

The items stored in the queue 310 then undergo a filter process 320 one at a time on a first-in, first-out basis. The filter process 320 examines the items in the queue 310 and supplies them to updated content buckets 330, which represents a series of memory regions that have been allocated to the users of the online social network. The filter process 320 selectively supplies the items in the queue 310 to the updated content buckets 330 in accordance with rules 335 that have been defined for the users. For example, the filter process 320 selectively supplies the items in the queue 310 to the updated content bucket 330 of user A in accordance with rules 335 that have been defined for user A; the filter process 320 selectively supplies the items in the queue 310 to the updated content bucket 330 of user B in accordance with rules 335 that have been defined for user B; and so forth. For each user, the rules 335 include an identification of those users or groups whose content he or she desires to track and specify the type of content updates or changes that he or she desires to track. By applying these rules to the filter process 320, the items stored in the queue 310 are stored in an updated content bucket 330 of a user only if such items represent content updates or changes of another user or group that he or she desires to track and are of the type that he or she desires to track.

The items stored in the updated content buckets 330 undergo output processing 340. The output processing 340 is carried out separately for each of the different updated content buckets 330 and in accordance with the rules 335 defined by the user who is associated with the updated content bucket. For each user, the rules 335 specify the frequency of the output processing 340, and the method of notification, whether by e-mail 342, a web page 344, or an RSS feed 346.

FIG. 4A is a schematic illustration of a web page used to specify notification settings that define the rules 335. In section 410, the user selects the type of content updates or changes he or she desires to track. In section 420, the user specifies those other users or groups whose content he or she desires to track. In section 430, the user selects the method of notification. In section 440, the user selects the frequency of notification. In section 450, the user has the option of turning off all notifications. Certain selections on the web page require the user to supply additional information through the “specify” hyperlink. For example, the user selects from a list of friends, users, bookmarked profiles, or groups in section 420 if one of these options is checked. In certain embodiments, the user is given the option to select all friends who are within 1, 2, or 3 degrees of separation. Also, if the user selects the RSS feed option in section 430, the user is asked to specify the URL to which the RSS feed will be transmitted and user ID and password that are required to access such URL.

FIG. 4B is a schematic illustration of a web page used to communicate to a user of the changes and updates to content of other users of the online social network. This web page is displayed when the user accesses his or her homepage of the online social network. This means that the user has selected at least the “Home page” option in section 430 of FIG. 4A. If the user has also selected the “E-mail” option and the “RSS feed” option, the user will be notified of the updates noted below by those methods as well. The first entry indicates that the user, Tammy, added new friends. The second entry indicates that the user, Sarah, received new testimonials. The third entry indicates that the user, Elton, updated his profile. The fourth entry indicates that the group, Giants Fan Club, added new members. These entries indicate that the user has selected at least the first, third, and fourth options in section 410. They also indicate that the user is tracking the updates of at least Tammy, Sarah, Elton, and the Giants Fan Club. For simplicity, the user is notified of a fixed number of most recent content updates (in this example, 4). The user can view more updates by accessing the hyperlink, “More Friend Updates.”

FIG. 5 is a flow diagram illustrating the process steps for filtering changes and updates to content in an online social network. These process steps are carried out by the application server 251 as it is carrying out the operations represented by blocks 310, 320 shown in FIG. 3, and represents one illustrative way of how changes and updates to content can be processed so that applicable users can be notified of such changes and updates.

In step 510, user inputs that reflect updates and changes to content are received and stored in a queue. The items stored in the queue are then processed one at a time and per user in accordance with steps 514-522. Step 514 represents the beginning of the loop. In this step, an item stored in the queue and a user are selected for processing. Each time through the loop, a next user is selected. If all users have been selected, then the first user and a next item stored in the queue are selected for processing.

In step 516, the selected user's rules are examined to see if the queue item being processed is of the type that the user is tracking. If it is, the process continues to step 518. If not, the process returns to the beginning of the loop. In step 518, the selected user's rules are examined to see if the queue item being processed is an update made by a user or group that the selected user is tracking. If it is, the process continues to step 520. If not, the process returns to the beginning of the loop. In step 520, the item being processed is stored in the selected user's updated content bucket. Step 522 checks to see if all items in the queue have been processed for all users. If this condition is true, the process ends. If not, the process returns to the beginning of the loop.

FIG. 6 schematically illustrates a web page that functions as a landing page for a particular user in an online social network and external content sources for the landing page. This landing page can be accessed several ways. First, it can be accessed from within the online social network by the user when the user logs into the online social network and navigates to this web page or by other users who clicks on a user ID or an image associated with this user, e.g., from a Friend Tracker page shown in FIG. 4B. Second, it can be accessed directly by typing in the associated URL into a web browser. Third, this page may be opened up to web crawlers of search engines and accessed when a user clicks on a search result that is hyperlinked to this page.

The web page shown in FIG. 6 includes multiple sections that contain different categories of content associated with the user. The user's profile information is provided in section 610. A list of the user's friends in the online social network and hyperlinks to their landing pages are provided in section 615. Section 620 displays the user's blog. In this example, the user is maintaining a blog at an external web site 661, e.g., Xanga.com, and the content of his or her blog is supplied from the external web site using an RSS feed. In a similar manner, the content of the user's pictures that is displayed in section 630 is supplied from an external web site 662 (e.g., Flickr) using an RSS feed, and the content of the user's videos that is displayed in section 640 is supplied from an external web site 663 (e.g., YouTube) using an RSS feed.

As a way to minimize the number of times an external web site is accessed for the necessary RSS feeds, all RSS feeds from external web sites are stored in a cache storage unit 650. All RSS feeds are also assigned a minimum lifetime and a maximum lifetime. When a landing page of a user is accessed and the landing page contains sections that rely on RSS feeds, the lifetime of each such RSS feed is checked. If it is below its minimum lifetime, the last cached version of the RSS feed is accessed. If it has exceeded the minimum lifetime, a query is issued to the external web site for the latest information. On a global basis, whenever an RSS feed reaches its maximum lifetime, a query is issued to the external web site for the latest information.

The query that is issued to an external web site for content associated with a user includes the user ID and password of that user as proof that access to the user's account maintained by the external web site is authorized. The user ID and password are provided by the user when the user sets up his or her landing page to retrieve content from external web sites through RSS feeds. The issued query is kept hidden at the user level and preferably encoded or encrypted so that the user ID and password contained in the query can be kept confidential.

FIG. 7 is a flow diagram illustrating the process steps carried out by a server computer for an online social network when notifying users of updates to landing pages and generating the landing pages upon request. More specifically, FIG. 7 illustrates the process where the landing page of one user (User A) is updated and the update notice and the updated landing page are transmitted to another user (User B). In step 710, the server computer receives updates to the landing page of User A from an external database. Each of the updates is associated with a particular RSS feed and is received in response to a query issued by the server computer to the external database for that update. When the updates are returned, they are stored in a cache storage unit. For each RSS feed, the external database is queried for a new update when: (1) [X] seconds has elapsed since the last update; or (2) the landing page of User A is accessed and [Y] seconds has elapsed since the last update. The received updates are placed in the queue 310 (shown in FIG. 3) and processed in the manner described above in conjunction with FIG. 3.

When the landing page of User A contains updates, User B is notified of one or more of these updates under certain conditions, e.g., the update is of the content type that User B desires to track and User A is part of a group of users that User B desires to track (step 712). User B is notified using a web page similar to the one that is schematically illustrated in FIG. 4B. A selection of any user on the notification page is interpreted as the server computer as a request for the landing page of that user (step 714). In response to this request, the server computer retrieves the content for User A's landing page that is stored locally in one of the databases managed by the server computer (step 716) and the content for User A's landing page that is maintained in one of the external databases (step 718). The content for User A's landing page that is maintained in one of the external databases is retrieved from the cache storage unit. Prior to the retrieval, a query may be issued to the external databases for a new update depending on how much time has elapsed since the most recent update for that content was stored in the cache storage unit. If more than [Y] seconds has elapsed since the last update, the query for new updates is issued to the external databases. When the new update is received, the content associated with the new updates is modified accordingly. In step 720, the landing page of User A is generated using the content retrieved in steps 716 and 718 and transmitted to User B.

FIG. 8 is a flow diagram illustrating the process steps carried out by a client computer connected to a server computer for an online social network when notifying a user of updates to a landing page of another user and displaying the landing page to the user. More specifically, FIG. 8 illustrates the process where updates to the landing page of one user (User A) are displayed on the client computer of another user (User B), and User B selects the landing page of User A that includes content from external sources for display. In step 810, the client computer displays a web page that indicates updates to the landing page of User A. This web page is similar to the one that is schematically illustrated in FIG. 4B. User B then clicks on the hyperlink associated with User A from this web page, and in response, the client computer issues a request for the landing page of User A to the server computer for the online social network (step 812). Then, in step 814, the client computer receives the landing page of User A that includes content managed by the server computer as well as content managed by another server computer. In step 816, the landing page of User A received in step 814 is displayed to User B.

In the embodiments of the present invention described above, RSS feeds are described as the mechanism for feeding content from the server computers of third party web sites to the server computer of the online social network. Other types of web feeds may be employed with the present invention. Some of these examples include atom feeds and feeds based on the SOAP protocol. It may even be possible to crawl the web pages of the third party web sites to collect the relevant information and store any updates in the cache storage unit.

While particular embodiments according to the invention have been illustrated and described above, those skilled in the art understand that the invention can take a variety of forms and embodiments within the scope of the appended claims. 

1. In a computer network including a server computer that maintains a user database and landing pages of the users, a method for processing user inputs at the server computer, comprising the steps of: (a) receiving updates to a landing page of a first user from another server computer in the computer network; (b) notifying a second user of the updates; (c) receiving a request for the landing page of the first user from the second user; (d) retrieving content of the first user as maintained by the server computer; (e) retrieving content of the first user as maintained by said another server computer in the computer network; (f) generating a landing page of the first user using the content retrieved in step (d) and step (e); and (g) transmitting the landing page to the second user for display.
 2. The method according to claim 1, wherein step (e) of retrieving includes the steps of issuing a query to said another server computer and receiving the content of the first user as maintained by said another server in response to the query.
 3. The method according to claim 2, wherein the query includes user ID and password of the first user, and the query is not visible to the second user.
 4. The method according to claim 1, wherein step (e) of retrieving includes the step of retrieving the content of the first user as maintained by said another server computer from a cache managed by the server computer.
 5. The method according to claim 1, wherein the second user is notified of the updates through a web page that identifies the first user and indicates the updates made to the landing page of the first user.
 6. The method according to claim 5, wherein the updates from said another server computer comprise an update to at least one of the first user's blog, the first user's photo collection, and the first user's video collection.
 7. The method according to claim 1, wherein the user database maintains connection data for each of the users, and the connection data for the first user comprises a connection to the second user and the connection data for the second user comprises a connection to the first user.
 8. The method according to claim 1, further comprising the step of receiving and storing inputs from the second user that specify one or more types of content that the second user desires to track.
 9. The method according to claim 8, further comprising the step of receiving and storing inputs from the second user that identify other users, including the first user, that the second user desires to track.
 10. A server computer in a network of server computers and client computers, comprising: a database of users that maintains a landing page for a first user and tracking preferences of a second user; and a processing unit that is programmed to carry out the steps of (i) receiving and storing updates to the landing page of the first user including updates from a client computer of the first user and updates from another server computer in the network, and (ii) if any of the updates is of a type included in said tracking preferences of the second user, notifying the second user of the updates.
 11. The server computer according to claim 10, wherein the tracking preferences of the second user include an indication of: (i) one or more types of content that are to be tracked, and (ii) those users who are to be tracked.
 12. The server computer according to claim 11, wherein those users who are to be tracked include the first user.
 13. The server computer according to claim 12, wherein the database maintains connection data for each of the users, and the connection data for the first user comprises a connection to the second user and the connection data for the second user comprises a connection to the first user.
 14. The server computer according to claim 10, wherein the processing unit is programmed to carry out the further steps of (iii) receiving a request for the landing page of the first user from the second user, (iv) generating the landing page of the first user, and (v) transmitting the landing page to the second user for display.
 15. The server computer according to claim 14, wherein the generated landing page includes content of the first user as maintained by the server computer and content of the first user as maintained by said another server computer.
 16. The server computer according to claim 15, further comprising a cache in which the content of the first user as maintained by said another server computer is stored.
 17. In a computer network comprising server computers that include a server computer for maintaining a user database and a landing page of a first user, and client computers that include a client computer of a second user, a method for processing user inputs at the client computer of the second user, comprising the steps of: (a) receiving a web page that indicates updates to the landing page of the first user from the server computer; (b) issuing a request for the landing page of the first user in response to an input made by the second user on the web page; (c) receiving the landing page of the first user from the server computer, the landing page of the first user including content of the first user as maintained by the server computer and content of the first user as maintained by another server computer in the computer network; and (d) displaying the landing page of the first user to the second user.
 18. The method according to claim 17, wherein the web page received in step (a) includes a hyperlink to the landing page of the first user and the input made by the second user comprises a click on the hyperlink.
 19. The method according to claim 17, wherein the content of the first user as maintained by said another server computer comprises at least one of the first user's blog, the first user's photo collection, and the first user's video collection.
 20. The method according to claim 17, wherein the user database maintains connection data for each of the users, and the connection data for the first user comprises a connection to the second user and the connection data for the second user comprises a connection to the first user. 